User interactions for a mapping application

ABSTRACT

The present disclosure relates to systems and processes for interacting with mapping applications. In one example, a virtual assistant server can efficiently communicate with a map server to provide a user with map data in response to spoken user requests received at a user device. In another example, communicatively coupled electronic devices can be synchronized such that a location marker generated on one device can be displayed on the other device. In another example, an electronic device can display simplified views of individual route directions that can be updated based on movement of the user or in response to user requests. In another example, an electronic device can selectively display an interface including a current location of a user or an interface including a route to a predicted destination based on contextual information associated with the user. The interfaces can include affordances for launching an associated mapping application.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/102,146 entitled “USER INTERACTIONS FOR A MAPPING APPLICATION”, filedon Aug. 13, 2018, which is a continuation of U.S. patent applicationSer. No. 14/836,754, now U.S. Pat. No. 10,066,959, entitled “USERINTERACTIONS FOR A MAPPING APPLICATION”, filed on Aug. 26, 2015, whichclaims priority to U.S. Provisional Patent Application 62/129,849entitled “USER INTERACTIONS FOR A MAPPING APPLICATION”, filed on Mar. 8,2015; U.S. Provisional Patent Application 62/044,944 entitled “USERINTERACTIONS FOR A MAPPING APPLICATION”, filed on Sep. 2, 2014; and U.S.Provisional Patent Application 62/044,993 entitled “REDUCED-SIZE USERINTERFACES FOR DYNAMICALLY UPDATED APPLICATION OVERVIEWS”, filed on Sep.2, 2014. The contents of these applications are hereby incorporated byreference in their entirety for all purposes.

FIELD

The present disclosure relates generally to mapping applications.

BACKGROUND

Mapping applications have become increasingly popular due to theproliferation of location-aware mobile electronic devices. Typically,users can interact with these mapping applications using touch-sensitivedisplays that are capable of both receiving user input and displayingportions of a map. While interacting with mapping applications in thisway can be intuitive and simple on many electronic devices, it can beproblematic when performed on compact mobile electronic devices havingsmaller displays. For example, it can be difficult to view routenavigation directions overlaid on a map when displayed on a display of acompact mobile electronic device, such as a watch. Similarly, it can bedifficult to type an address using a virtual keyboard displayed on thedisplay of a compact mobile electronic device.

BRIEF SUMMARY

Some mapping application techniques using electronic devices, however,are generally cumbersome and inefficient. For example, some existingtechniques use a complex and time-consuming user interface, which mayinclude multiple key presses or keystrokes. Existing techniques requiremore time than necessary, wasting user time and device energy. Thislatter consideration is particularly important in battery-operateddevices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for interacting withmapping applications. Such methods and interfaces optionally complementor replace other methods for interacting with mapping applications. Suchmethods and interfaces reduce the cognitive burden on a user and producea more efficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

The present disclosure relates to systems and processes for interactingwith mapping applications. In one example, a virtual assistant servercan efficiently communicate with a map server to provide a user with mapdata in response to spoken user requests received at a user device. Inanother example, communicatively coupled electronic devices can besynchronized such that a location marker generated on one device can bedisplayed on the other device. In yet another example, an electronicdevice can display simplified views of individual route directions thatcan be updated based on movement of the user or in response to userrequests. In yet another example, an electronic device can selectivelydisplay an interface including a current location of a user or aninterface including a route to a predicted destination based oncontextual information associated with the user. The interfaces caninclude affordances for causing the electronic device to launch anassociated mapping application.

In some embodiments, a computer-implemented method at one or moreservers is described. The method includes: receiving, from an electronicdevice: data corresponding to an audio input comprising user speech; andcontextual data representing a context of the user speech; generating atextual representation of the user speech based on the datacorresponding to the audio input; transmitting, to a map server, thetextual representation of the user speech and the contextual data;receiving, from the map server, map data; and transmitting, to theelectronic device, the map data.

In some embodiments, a system is described. The system includes: meansfor receiving data corresponding to an audio input comprising userspeech; means for receiving contextual data representing a context ofthe user speech; means for generating a textual representation of theuser speech based on the data corresponding to the audio input; meansfor transmitting, to a map server, the textual representation of theuser speech and the contextual data; means for receiving, from the mapserver, map data; and means for transmitting, to the electronic device,the map data.

In some embodiments, a computer-implemented method at a first electronicdevice is described. The method includes: causing, on a display of thefirst electronic device, a display of a map; determining whether a firstrequest to mark a first location on the map has been received; and inaccordance with a determination that the first request to mark the firstlocation on the map has been received: causing, on the display of thefirst electronic device, a display of a first location marker on the mapat a position within the display corresponding to the first location;and transmitting, to a second electronic device, a first set ofgeographic coordinates corresponding to the first location.

In some embodiments, a system is described. The system includes: meansfor causing, on a display of a first electronic device, a display of amap; means for determining whether a first request to mark a firstlocation on the map has been received; means for causing, on the displayof the first electronic device, a display of a first location markeroverlaid on the map at a position within the display corresponding tothe first location in accordance with a determination that the firstrequest to mark the first location on the map has been received; andmeans for transmitting, to a second electronic device, a first set ofgeographic coordinates corresponding to the first location in accordancewith a determination that the first request to mark the first locationon the map has been received.

In some embodiments, a computer-implemented method at an electronicdevice is described. The method includes: receiving an ordered set ofroute directions for navigating a route from a start location to an endlocation, wherein the route comprises a plurality of segments; andcausing, on a display of the electronic device, a display of first routedirection interface associated with a first route direction of the setof route directions, wherein the first route direction is associatedwith a first segment of the plurality of segments and comprises a firstdirectional instruction and a first segment identifier associated withthe first segment, and wherein the first route direction interfacecomprises: a first textual description of the first directionalinstruction and the first segment identifier; and a first visualrepresentation of the first directional instruction.

In some embodiments, a system is described. The system includes: meansfor receiving an ordered set of route directions for navigating a routefrom a start location to an end location, wherein the route comprises aplurality of segments; and means for causing a display of first routedirection interface associated with a first route direction of the setof route directions, wherein the first route direction is associatedwith a first segment of the plurality of segments and comprises a firstdirectional instruction and a first segment identifier associated withthe first segment, and wherein the first route direction interfacecomprises: a first textual description of the first directionalinstruction and the first segment identifier; and a first visualrepresentation of the first directional instruction.

In some embodiments, a method at an electronic device with a display isdescribed. The method includes: detecting a display triggering event; inaccordance with a detection of the display triggering event, obtainingcontextual data representing a context of the electronic device;determining, based on the contextual data, whether a user is likely tobe traveling to a destination within a threshold length of time; inaccordance with a determination that the user is likely to be travelingto the destination within the threshold length of time, causing, on thedisplay, a display of a first interface representing a mappingapplication, wherein the first interface representing the mappingapplication comprises: a first affordance for launching the mappingapplication, and a set of information associated with traveling to thedestination; and in accordance with a determination that the user is notlikely to be traveling to the destination within the threshold length oftime, causing, on the display, a display of a second interfacerepresenting the mapping application, wherein the second interfacerepresenting the mapping application comprises: a second affordance forlaunching the mapping application, and a visual representation of alocation of the electronic device.

In some embodiments, a system is described. The system includes: meansfor detecting a display triggering event; means for obtaining contextualdata representing a context of the electronic device in accordance witha detection of the display triggering event; means for determining,based on the contextual data, whether a user is likely to be travelingto a destination within a threshold length of time; means for causing adisplay of a first interface representing a mapping application inaccordance with a determination that the user is likely to be travelingto the destination within the threshold length of time, wherein thefirst interface representing the mapping application comprises: a firstaffordance for launching the mapping application, and a set ofinformation associated with traveling to the destination; and means forcausing a display of a second interface representing the mappingapplication in accordance with a determination that the user is notlikely to be traveling to the destination within the threshold length oftime, wherein the second interface representing the mapping applicationcomprises: a second affordance for launching the mapping application,and a visual representation of a location of the electronic device.

In some embodiments, one or more servers are described. The one or moreservers include a processing unit configured to: receive, from anelectronic device: data corresponding to an audio input comprising userspeech; and contextual data representing a context of the user speech;generate a textual representation of the user speech based on the datacorresponding to the audio input; transmit, to a map server, the textualrepresentation of the user speech and the contextual data; receive, fromthe map server, map data; and transmit, to the electronic device, themap data.

In some embodiments, a first electronic device is described. The firstelectronic device comprises a display unit and a processing unit coupledto the display unit, the processing unit configured to: cause, on thedisplay unit of the first electronic device, a display of a map;determine whether a first request to mark a first location on the maphas been received; and in accordance with a determination that the firstrequest to mark the first location on the map has been received: cause,on the display unit of the first electronic device, a display of a firstlocation marker on the map at a position within the displaycorresponding to the first location; and transmit, to a secondelectronic device, a first set of geographic coordinates correspondingto the first location.

In some embodiments, an electronic device is described. The electronicdevice includes a display unit and a processing unit coupled to thedisplay unit, the processing unit configured to: receive an ordered setof route directions for navigating a route from a start location to anend location, wherein the route comprises a plurality of segments; andcause, on a display unit of the electronic device, a display of firstroute direction interface associated with a first route direction of theset of route directions, wherein the first route direction is associatedwith a first segment of the plurality of segments and comprises a firstdirectional instruction and a first segment identifier associated withthe first segment, and wherein the first route direction interfacecomprises: a first textual description of the first directionalinstruction and the first segment identifier; and a first visualrepresentation of the first directional instruction.

In some embodiments, an electronic device is described. The electronicdevice includes a display unit and a processing unit coupled to thedisplay unit, the processing unit configure to: detect a displaytriggering event; in accordance with a detection of the displaytriggering event, obtain contextual data representing a context of theelectronic device; determine, based on the contextual data, whether auser is likely to be traveling to a destination within a thresholdlength of time; in accordance with a determination that the user islikely to be traveling to the destination within the threshold length oftime, cause, on the display unit, a display of a first interfacerepresenting a mapping application, wherein the first interfacerepresenting the mapping application comprises: a first affordance forlaunching the mapping application, and a set of information associatedwith traveling to the destination; and in accordance with adetermination that the user is not likely to be traveling to thedestination within the threshold length of time, cause, on the displayunit, a display of a second interface representing the mappingapplication, wherein the second interface representing the mappingapplication comprises: a second affordance for launching the mappingapplication, and a visual representation of a location of the electronicdevice.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for interacting with mapping applications, thereby increasingthe effectiveness, efficiency, and user satisfaction with such devices.Such methods and interfaces may complement or replace other methods forinteracting with mapping applications.

DESCRIPTION OF THE FIGURES

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some examples.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some examples.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some examples.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with some examples.

FIGS. 4A and 4B illustrate an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someexamples.

FIG. 5A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some examples.

FIG. 5B illustrates a portable multifunction device having atouch-sensitive display in accordance with some examples.

FIG. 6 illustrates a block diagram of an exemplary system for providingmapping services to a mapping application according to various examples.

FIG. 7 illustrates an exemplary process for interacting with mappingapplications according to various examples.

FIG. 8 illustrates another exemplary process for interacting withmapping applications according to various examples.

FIGS. 9-11 illustrate example interfaces for interacting with mappingapplications according to various examples.

FIG. 12 illustrates another exemplary process for interacting withmapping applications according to various examples.

FIGS. 13-18 illustrate example interfaces for interacting with mappingapplications according to various examples.

FIG. 19 illustrates another exemplary process for interacting withmapping applications according to various examples.

FIGS. 20-22 illustrate example interfaces for interacting with mappingapplications according to various examples.

FIGS. 23-26 illustrate functional block diagrams of electronic devicesaccording to various examples.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

The present disclosure relates to systems and processes for interactingwith mapping applications. In one example, a virtual assistant servercan efficiently communicate with a map server to provide a user with mapdata in response to spoken user requests received at a user device. Inanother example, communicatively coupled electronic devices can besynchronized such that a location marker generated on one device can bedisplayed on the other device. In yet another example, an electronicdevice can display simplified views of individual route directions thatcan be updated based on movement of the user or in response to userrequests. In yet another example, an electronic device can selectivelydisplay an interface including a current location of a user or aninterface including a route to a predicted destination based oncontextual information associated with the user. The interfaces caninclude affordances for causing the electronic device to launch anassociated mapping application.

Below, FIGS. 1A-1B, 2, 3, and 5A-5B provide a description of exemplarydevices for interacting with mapping applications. FIGS. 4A-4B, 9-11,13-18, and 20-22 illustrate exemplary user interfaces that can bedisplayed on these exemplary devices.

Although the following description uses terms first, second, etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 may include one or more computer readable storage mediums.The computer readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2 ). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2 ) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2 ).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web-pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereas touchsensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIGS. 1Aand 1B show an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 may include charge-coupleddevice (CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for videoconferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIGS. 1Aand 1B show proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIGS. 1A and1B show accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A, 1B and 3 . Device/globalinternal state 157 includes one or more of: active application state,indicating which applications, if any, are currently active; displaystate, indicating what applications, views or other information occupyvarious regions of touch screen display 112; sensor state, includinginformation obtained from the device's various sensors and input controldevices 116; and location information concerning the device's locationand/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact) determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   video player module 145;    -   music player module 146;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which merges video player        module 145 and music player module 146;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conference 139,e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web-pages or portionsthereof, as well as attachments and other files linked to web-pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web-page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video. Additional description of theonline video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the content of which is herebyincorporated by reference in its entirety.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. For example, video player module 145may be combined with music player module 146 into a single module (e.g.,video and music player module 152, FIG. 1A). In some embodiments, memory102 may store a subset of the modules and data structures identifiedabove. Furthermore, memory 102 may store additional modules and datastructures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170(e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(e.g., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that may be implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icons 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touchscreen 504. Alternatively, or inaddition to touchscreen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touchscreen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500. As used here, the term “intensity” of a contact (or touch)on touchscreen 504 (or the touch-sensitive surface) refers to the forceor pressure (force per unit area) of a touch (e.g., a finger) on thetouchscreen.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, entitled “Device, Method, and GraphicalUser Interface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, entitled “Device, Method, and GraphicalUser Interface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth™, nearfield communication (“NFC”), cellular and/or other wirelesscommunication techniques. Device 500 can include input mechanisms 506and/or 508. Input mechanism 506 may be a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 508may be a button, in some examples.

Input mechanism 508 may be a microphone, in some examples. Computingdevice 500 can include various sensors, such as GPS sensor 532,accelerometer 534, directional sensor 540 (e.g., compass), gyroscope536, motion sensor 538, and/or a combination thereof, all of which canbe operatively connected to I/O section 514.

Memory 518 of computing device 500 can be a non-transitory computerreadable storage medium, for storing computer-executable instructions,which, when executed by one or more computer processors 516, forexample, can cause the computer processors to perform the techniquesdescribed above, including processes 700, 800, 1200, and 1900 (FIGS. 7,8, 12, and 19 ). The computer-executable instructions can also be storedand/or transported within any non-transitory computer readable storagemedium for use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Computing device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of device 100, 300, and/or 500 (FIGS. 1, 3, and 5 ). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementationsfocus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe third threshold results in a third operation. In some embodiments, acomparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective option or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm may be an unweighted sliding-average smoothing algorithm, atriangular smoothing algorithm, a median filter smoothing algorithm,and/or an exponential smoothing algorithm. These smoothing algorithmsmay eliminate narrow spikes or dips in the intensities of the swipecontact for purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments the contact-detection intensity threshold is zero.In some embodiments the contact-detection intensity threshold is greaterthan zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90% or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the term “open application” or “executing application”refers to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application may be any one of thefollowing types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes) which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

FIG. 6 illustrates exemplary system 600 for implementing a virtualassistant and for providing mapping services according to variousexamples. The terms “virtual assistant,” “digital assistant,”“intelligent automated assistant,” or “automatic digital assistant,” canrefer to any information processing system that interprets naturallanguage input in spoken and/or textual form to infer user intent, andperforms actions based on the inferred user intent. For example, to acton an inferred user intent, the system can perform one or more of thefollowing: identifying a task flow with steps and parameters designed toaccomplish the inferred user intent; inputting specific requirementsfrom the inferred user intent into the task flow; executing the taskflow by invoking programs, methods, services, APIs, or the like; andgenerating output responses to the user in an audible (e.g., speech)and/or visual form.

A virtual assistant can be capable of accepting a user request at leastpartially in the form of a natural language command, request, statement,narrative, and/or inquiry. Typically, the user request seeks either aninformational answer or performance of a task by the virtual assistant.A satisfactory response to the user request can include either provisionof the requested informational answer, performance of the requestedtask, or a combination of the two. For example, a user can ask thevirtual assistant a question, such as “Where am I right now?” Based onthe user's current location, the virtual assistant can answer, “You arein Central Park.” The user can also request the performance of a task,for example, “Please remind me to call Mom at 4 PM today.” In response,the virtual assistant can acknowledge the request and then create anappropriate reminder item in the user's electronic schedule. Duringperformance of a requested task, the virtual assistant can sometimesinteract with the user in a continuous dialogue involving multipleexchanges of information over an extended period of time. There arenumerous other ways of interacting with a virtual assistant to requestinformation or performance of various tasks. In addition to providingverbal responses and taking programmed actions, the virtual assistantcan also provide responses in other visual or audio forms (e.g., astext, alerts, music, videos, animations, etc.) and possibly usingmultiple devices (e.g., output text to speech via a phone headset anddisplay text on a TV).

An example of a virtual assistant is described in Applicants' U.S.Utility application Ser. No. 12/987,982 for “Intelligent AutomatedAssistant,” filed Jan. 10, 2011, the entire disclosure of which isincorporated herein by reference.

As shown in FIG. 6 , in some examples, a virtual assistant can beimplemented according to a client-server model. The virtual assistantcan include a client-side portion executed on user devices 602 and/or604, and a server-side portion executed on a server system 610. Userdevice 602 and/or 604 can include any electronic device, such as device100, 300, or 500, and can communicate with server system 610 through oneor more networks 608, which can include the Internet, an intranet, orany other wired or wireless public or private network. The client-sideportion executed on user device 602 or 604 can provide client-sidefunctionalities, such as user-facing input and output processing andcommunications with server system 610. Server system 610 can provideserver-side functionalities for any number of clients residing onrespective user devices 602 and 604.

Server system 610 can include one or more virtual assistant servers 614that can include a client-facing I/O interface 622, one or moreprocessing modules 618, data and model storage 620, and an I/O interfaceto external services 616. The client-facing I/O interface 622 canfacilitate the client-facing input and output processing for virtualassistant server 614. The one or more processing modules 618 can utilizedata and model storage 620 to determine the user's intent based onnatural language input and can perform task execution based on inferreduser intent. In some examples, virtual assistant server 614 cancommunicate with external services, such as telephony services, calendarservices, information services, messaging services, navigation services,and the like, through network(s) 608 for task completion or informationacquisition. The I/O interface to external services 616 can facilitatesuch communications.

In the example shown in FIG. 6 , the external services can includemapping services provided by server system 623. Server system 623 canprovide server-side functionalities for any number of clients residingon respective user devices 602 and 604 and can include one or more mapservers 624 that can include an I/O interface 626, one or moreprocessing modules 628, and map and navigation data storage 630. The I/Ointerface 626 can facilitate the client-facing and/or server-facinginput and output processing for map server 624. The one or moreprocessing modules 628 can utilize map and navigation data storage 630to provide any of various mapping services, such as providingappropriate map tiles for display on user device 602 and/or 604, providegeocoding and reverse geocoding functions, provide navigation androuting functions to determine directions from a start location to andend location, provide traffic information, and the like. Server system610 and/or 623 can be implemented on one or more standalone dataprocessing devices or a distributed network of computers. In someexamples, server system 610 and/or 623 can employ various virtualdevices and/or services of third party service providers (e.g.,third-party cloud service providers) to provide the underlying computingresources and/or infrastructure resources of server system 610 and/or623.

In some examples, the client-side portion executed on user devices 602and 604 can include mapping applications, which can provide client-sidefunctionalities, such as user-facing input and output processing andcommunications with server system 610 and/or 623. For example, themapping applications can request map data from server system 623 viaserver system 610 and/or can request map data from server system 623directly. Additionally, in some examples, one user device (e.g., userdevice 602) can be communicatively coupled with another user device(e.g., user device 604) via a direct communication connection, such asBluetooth, NFC, BTLE, or the like, or via a wired or wireless network,such as a local Wi-Fi network. In these examples, one user device (e.g.,user device 604) can act as a proxy between the other user device (e.g.,user device 602) and server system 610 and/or server system 623 byreceiving data or requests for data from the other user device andtransmitting the data or the requests for data to server system 610and/or server system 623. Additionally, in these examples, the proxyuser device can receive data or requests for data from server system 610and/or server system 623 and can transmit the data or request for datato the other user device. By allowing one user device to act as a proxyfor another advantageously provides a user device having limitedcommunication capabilities and/or limited battery power, such as a watchor other compact electronic device, with that ability to access virtualassistant services provided by server system 610 and mapping servicesprovided by server system 623 by leveraging the communicationcapabilities and/or battery power of another user device, such as amobile phone, laptop computer, tablet computer, or the like. While onlytwo user devices 602 and 604 are shown in FIG. 6 , it should beappreciated that system 600 can include any number and type of userdevices that operate independently or that are configured in a proxyconfiguration to communicate with server systems 610 and 623.

Although the functionality of the virtual assistant and mapping servicesare shown in FIG. 6 as including both a client-side portion and aserver-side portion, in some examples, the functions of the assistantand/or mapping services can be implemented as a standalone applicationinstalled on a user device. In addition, the division of functionalitiesbetween the client and server portions of the virtual assistant and/ormapping services can vary in different examples. For instance, in someexamples, the client executed on user device 602 or 604 can be athin-client that provides only user-facing input and output processingfunctions, and delegates all other functionalities of the virtualassistant and/or mapping services to a backend server.

FIG. 7 illustrates an exemplary process 700 for interacting with amapping application using a voice commands according to variousexamples. In some examples, process 700 can be performed using a systemsimilar or identical to system 600, shown in FIG. 6 . In these examples,the blocks of process 700 can be performed by user device 602 and/or604, virtual assistant server system 610, and mapping server system 623.Specifically, the blocks on the left side of FIG. 7 can be performed byuser device 602 and/or 604, the blocks in the center of FIG. 7 can beperformed by virtual assistant server system 610, and the blocks on theright side of FIG. 7 can be performed by mapping server system 623.

At block 702, an audio input including user speech can be received at auser device. The user speech can include an instruction, request, or anyother desired input for a mapping application. For example, the userspeech can include a request for route navigation directions from theuser's current location to a point of interest, an instruction tozoom-in or zoom-out from a displayed view of a map, an input containingan address or name of a point of interest, or the like. In someexamples, a user device (e.g., user device 602 or 604) can receive theaudio input that includes the user's speech via a microphone. Themicrophone can convert the audio input into an analog or digitalrepresentation, and provide the audio data to one or more processors ofthe device. The data representing the audio input can be transmitted toone or more servers for processing. For instance, in some examples, userdevice 602 or 604 can receive an audio input that represents the user'sspeech, convert the audio input into an analog or digitalrepresentation, and transmit the data representing the audio input tovirtual assistant server 614 of server system 610 via network(s) 608. Inother examples, one user device (e.g., user device 604) can be used as aproxy between another user device (e.g., user device 602) and the serversystems 610 and 623. In these examples, user device 602 can receive theaudio input that represents the user's speech, convert the audio inputinto an analog or digital representation, transmit the data representingthe audio input to user device 604, and user device 604 can transmit thedata representing the audio input to virtual assistant server 614 ofserver system 610 via network(s) 608.

Additionally, in some examples, contextual data associated with the userinput can be transmitted along with the data representing the audioinput at block 702. In general, the contextual data can include any typeof information associated with the user input that can be used to inferthe user's intent. In some examples, the contextual data can includesensor information from user device 602 or 604, such as lighting,ambient noise, ambient temperature, images or videos of the surroundingenvironment, current time, distance to another object, and the like. Thecontextual information can additionally or alternatively includeinformation associated with the physical state of user device 602 or604, such as the device orientation, device location, devicetemperature, power level, speed, acceleration, motion patterns, cellularsignal strength, etc., or the software state of user device 602 or 604,such as running processes, installed programs, past and present networkactivities, background services, error logs, resources usage, contentsdisplayed on the device, contents of a portion of a map displayed on thedevice, length of time that a current view has been displayed on thedevice, length of time since receiving a user input, length of time anapplication has been opened or running, etc. Any of these types ofcontextual information can be provided to the virtual assistant server614 as contextual information associated with the user input.

At block 704, data corresponding to the audio input and the contextualdata transmitted by the user device at block 702 can be received by oneor more virtual assistant servers. For example, virtual assistant server614 of server system 610 can receive the data corresponding to the audioinput and the contextual data transmitted by user device 602 or 604 vianetwork(s) 608.

At block 706, the one or more virtual assistant servers can performspeech-to-text conversion on the data corresponding to the audio inputto convert the user speech into a textual representation of the userspeech. The user speech can be converted using any known speech-to-textconversion process. For example, virtual assistant server 614 of serversystem 610 can perform a speech-to-text conversion on the audio inputreceived at block 704.

At block 708, the one or more virtual assistant servers can transmit thetextual representation of the user speech generated at block 706 and thecontextual data received at block 704 to one or more map servers. Forexample, virtual assistant server 614 of server system 610 can transmitthe textual representation of the user speech generated at block 706 andthe contextual data received at block 704 to map server 624 of serversystem 623 via network(s) 608. In some examples, the textualrepresentation may not also be transmitted to the user device.

At block 710, the textual representation of the user speech and thecontextual data transmitted by the one or more virtual assistant serversat block 708 can be received by one or more map servers. For example,map server 624 of server system 623 can receive the textualrepresentation of the user speech and the contextual data transmitted byvirtual assistant server 614 via network(s) 608.

At block 712, the one or more map servers can process the textualrepresentation of the user speech using the contextual data to infer theuser's intent. Based on the inferred intent, the one or more servers canidentify a task flow with steps and parameters designed to accomplishthe inferred user intent, inputting input requirements from the inferreduser intent into the task flow, execute the task flow by invokingprograms, methods, services, APIs, or the like, and/or generate map datato be provided to the user of the user device in response to their audioinput. In some examples, the map data can include map tiles to bedisplayed on a user device, route navigation information containingdirections from a start location to an end location, geographiccoordinates, textual descriptions and/or visual representations of alocation, a point of interest, an object of interest, or the like. Forexample, map server 624 can process the textual representation of theuser speech using the contextual data received at block 710 to determinethe appropriate map data to provide to the user. If, for example, theuser speech included the request “Give me directions to the park,” mapserver 624 can process the request by using the contextual data todetermine which park the user is likely referring to. The user's currentlocation, the presence or absence of a park within the portion of a mapbeing displayed by the user device, and the like, can be used to makethis determination. Once a specific park is identified, a navigationalgorithm can be performed using the user's current location as a startpoint and the location of the park as an end point. The algorithm canproduce map data containing the route from the user to the park. Similarprocesses can be performed to respond to other user requests and inputswith appropriate map data.

At block 714, the one or more map servers can transmit the map dataoutput by the processing of the textual representation of user speechperformed at block 712 to the one or more virtual assistant servers. Forexample, map server 624 of server system 623 can transmit the map datagenerated at block 712 to virtual assistant server 614 of server system610 via network(s) 608.

At block 716, the map data transmitted by the one or more map andnavigation servers at block 714 can be received by one or more virtualassistant servers. For example, virtual assistant server 614 can receivethe map data transmitted by map server 624 of server system 623 vianetwork(s) 608. In other examples, at block 714, the one or more mapservers can instead transmit the map data directly to the user device,rather than to the one or more virtual assistant servers.

At block 718, the one or more virtual assistant servers can transmit themap data received at block 716 to the user device. For example, virtualassistant server 614 of server system 610 can transmit the map datareceived at block 716 to user device 602 or 604 via network(s) 608.

At block 720, the map data transmitted by the one or more virtualassistant servers at block 718 can be received by the user device. Forexample, user device 602 or 604 can receive the map data transmitted byvirtual assistant server 614 via network(s) 608. In some examples, wherea user device is used as a proxy for another user device, block 720 canfurther include transmitting the map data to the proxied user device.

Using process 700, a mapping service can quickly respond to a request orother user input in the form of user speech. In particular, process 700advantageously routes the converted textual representation of userspeech and contextual information from the virtual assistant serverdirectly to the map and navigation server for processing. This providesa speed improvement over existing systems that return the textualrepresentation of user speech from the virtual assistant server to theuser device and that require the user device to then transmit thereceived textual representation of user speech and the contextualinformation to the map and navigation server. The speed improvement canbe particularly noticeable when the virtual assistant server and the mapserver are located in close proximity or are connected to the samenetwork, resulting in the communication speed between the virtualassistant server and the map server being greater than the communicationspeed between the user device and the map server.

FIG. 8 illustrates an exemplary process 800 for synchronizing locationmarkers entered into mapping applications between communicativelycoupled electronic devices according to various examples. In someexamples, process 800 can be performed using electronic devices similaror identical to device 100, 300, 500, 602, or 604.

At block 802 of process 800, a first electronic device can display a mapon a display of the device. For example, user device 602 or 604 candisplay a map similar to that shown in interface 900 of FIG. 9 .

At block 804, the first electronic device can determine whether arequest to mark a location on the displayed map has been received. Forexample, user device 602 or 604 can determine whether a request to marka location on the map displayed at block 802 has been received. Therequest can be input into the first electronic device in any desiredmanner. For example, the request can be made by a selection of a buttondisplayed on the displace of the first electronic device, a depressionof a physical button, a rotation of a rotatable mechanism, a touch at alocation on a touch-sensitive display corresponding to the desiredlocation of the map to be marked, a touch and hold on a location on atouch-sensitive display corresponding to the desired location of the mapto be marked, a press at a location on a pressure-sensitive displaycorresponding to the desired location of the map to be marked, or thelike. To illustrate, FIG. 10 shows a request to mark a location on themap displayed in FIG. 9 being made by a user touching and holding anobject (e.g., a finger) on the touch-sensitive display of the firstelectronic device at touch location 1002. If it is determined at block804 that a request to mark a location on the map has been received,process 800 can proceed to block 806. However, if it is insteaddetermined that no request to mark a location has been received, process800 can repeat block 804. Block 804 can be repeated periodically,intermittently, or at any other desired frequency or interval of time todetermine if a request to mark a location on the map has been received.

At block 806, the first electronic device can display a location markeroverlaid on the map at the location requested by the user at block 804.The location marker can include any element that is visually distinctfrom the underlying map to allow a user to identify the marked location.For example, user device 602 or 604 can display a location markersimilar or identical to location marker 1102, shown in FIG. 11 .Location marker 1102 can be overlaid on the map at a positioncorresponding to the location of the user's request received at block804. Location marker 1102 can be associated with geographic coordinatesof the location requested to be marked at block 804 and/or a textualdescription of the requested location, such as a street name, address,city, country, zip code, or the like. In some examples, a description1104 containing some or all of this associated information can bedisplayed overlaid on the map and near location marker 1102. In someexamples, a selection of description 1104 and/or location marker 1102can cause the first electronic device to display additional or moredetailed information about the marked location. The display of locationmarker 1102 and description 1104 advantageously allows a user toidentify a location of interest within a map and to view additionalinformation associated with the selected location, such as street name,address, city, country, zip code, or the like. This can be particularlybeneficial when performed on electronic devices having limited inputcapabilities, such as wearable electronic devices (e.g., a watch) orother compact devices, since it can be difficult to select a specificlocation without additional controls, such as a mouse, touchpad, or thelike. In some examples, block 806 can further include storing, by thefirst electronic device, the geographic coordinates and otherinformation associated with the location marker.

At block 808, the first electronic device can transmit the geographiccoordinates associated with the location marker displayed at block 806to a second electronic device. In some examples, other informationassociated with the location marker displayed at block 806, such as astreet name, address, city, country, zip code, or the like, can also betransmitted to the second electronic device. The second electronicdevice can be a device that has been paired with the first electronicdevice, is associated with a same user account as the first electronicdevice, or is otherwise associated with the first electronic device. Forexample, user device 602 (alternatively user device 604) can transmitthe geographic coordinates of the location requested to be marked atblock 804 to user device 604 (alternatively user device 602) via adirect communication connection, such as Bluetooth, NFC, BTLE, or thelike, or via a wired or wireless network, such as a local Wi-Fi network.In some examples, the second electronic device can store the geographiccoordinates and other information associated with the location marker.In other examples, user device 602 (alternatively user device 604) cantransmit the geographic coordinates of the location requested to bemarked at block 804 to a server or remote database that can be accessedby user device 604 (alternatively user device 602).

After transmitting the geographic coordinates and, optionally, the otherinformation associated with the location marker to the second electronicdevice, process 800 can return to block 804. Blocks 804, 806, and 808can repeatedly be performed to allow a user to mark any number oflocations. In some examples, an additional location marker can bedisplayed overlaid on the map each time block 806 is performed. In theseexamples, the geographic coordinates and other information associatedwith the additional location markers can also be stored on the firstelectronic device. In other examples, the location marker displayed atblock 806 can replace one or more existing location markers previouslydisplayed on the map. In these examples, the geographic coordinates andother information associated with the new location marker can replacepreviously stored geographic coordinates and other informationassociated with one or more older location markers.

In some examples, the second electronic device can use the geographiccoordinates (and, optionally, other information associated with thelocation marker) provided by the first electronic device at block 808 todisplay a location marker overlaid on a map being displayed by thesecond electronic device. The location marker can be the same ordifferent than the location marker displayed by the first electronicdevice. This advantageously allows a user to open a mapping applicationon the first electronic device, mark a location of interest within themapping application, and view the marked location of interest in amapping application on a different electronic device.

In some examples, process 800 can be performed by both the firstelectronic device and the second electronic device such that a requestto mark a location on one device can cause the same location to bemarked on the other electronic device. In these examples, the electronicdevice receiving the geographic coordinates and other informationassociated with a location marker can store that information in additionto previously stored information associated with other location markersor can replace the previously stored information associated with othermarker(s) with the newly received information. In other examples,process 800 can be performed to synchronize marked locations betweenmore than two electronic devices. In these examples, block 808 caninclude transmitting the geographic coordinates (and, optionally, otherinformation associated with the location marker and with the locationrequested to be marked at block 804) to the other electronic devices.Moreover, process 800 can also be performed by the additional electronicdevices.

FIG. 12 illustrates an exemplary process 1200 for displaying routenavigation directions according to various examples. In some examples,process 1200 can be performed using electronic devices similar oridentical to device 100, 300, 500, 602, or 604.

At block 1202, an electronic device can receive a set of routedirections for navigating a route from a start location to an endlocation. For example, an electronic device, such as user device 602 or604, can receive a set of route navigation directions from a map server,such as map server 624 of server system 623. In other examples, theelectronic device can instead generate the route navigation directionslocally on the electronic device. In some examples, the route caninclude one or more segments corresponding to roads, highways, or otherpredefined or arbitrary portions of the route. In these examples, theset of route directions can include an ordered set of directions thatcan each include a directional instruction (e.g., an instruction toturn, and instruction to travel straight, or the like) and a name orother identifier of an associated segment of the route (e.g., aroad/street/highway name, unique identifier, or the like). For example,one direction of the set of route directions can be “Turn Right on AStreet.” In this example, the direction includes a directionalinstruction “Turn Right” and a name of the associated segment “AStreet.” The other directions of the set of route directions cansimilarly include a directional instruction and the name or otheridentifier of an associated segment of the route.

At block 1204, the electronic device (e.g., user device 602 or 604) candisplay a route direction interface representing a direction of the setof route directions received or generated at block 1202. In someexamples, the direction represented by the route direction interface canbe the first direction in the ordered set of route directions. FIG. 13shows an example route direction interface 1300 that can be displayed bythe electronic device at block 1204. As shown, interface 1300 caninclude a textual representation 1302 of the route direction. Thetextual representation 1302 can include a textual representation of boththe directional instruction (e.g., “Turn Right”) and the segment name oridentifier (e.g., “1^(st) Street”) of the displayed direction. Interface1300 can further include a visual representation 1304 of the directionalinstruction of the displayed direction. The visual representation 1304can include a simplified visual representation of the directionalinstruction, such as an image of a directional arrow, to allow a user toquickly and easily recognize the next direction to make. In someexamples, interface 1300 can further include an estimated time ofarrival (“ETA”) 1306 that can be calculated by the electronic device orthe map server based on the current time, distance to the destination,type of roads being traveled, traffic conditions, the user's mode of thetransportation, or the like. Interface 1300 can further include acurrent time indicator 1308 that provides a textual and/or visualrepresentation of the current time. Interface 1300 can further includepage indicators 1310 that can include a number of indicators (e.g.,circles) corresponding to a number of directions in the ordered set ofdirections and the current direction being displayed (represented by thefilled-in circle). In some examples, the route direction interface canexclude a view of a map or other visual representation of one or moresegments of the route. This advantageously removes clutter from thedisplay and allows a user to easily view the directional instruction andthe segment identifier.

Referring back to FIG. 12 , at block 1206, the electronic device (e.g.,user device 602 or 604) can determine if the user's location has changedor if the user's location changed from a location corresponding to theroute direction displayed at block 1204 to a location corresponding to adifferent route direction in the ordered set of route directions. Insome examples, this can include determining geographic coordinates ofthe electronic device using any desired location determinationtechnology, such as GPS or GLONASS (e.g., using GPS module 135, sensors359, or GPS sensor 532), Wi-Fi or cellular (e.g., using RF circuitry108, network communication interface 360, or communication unit 530), orthe like. For example, the electronic device can receive locationinformation from GPS satellites, nearby Wi-Fi base stations, and/ornearby cell towers, as described in U.S. patent application Ser. No.12/040,283, “Location Determination,” filed Feb. 29, 2008; Ser. No.12/103,330, “Location Determination Using Formula,” filed Apr. 15, 2008;and Ser. No. 12/122,339, “Location Determination,” filed May 16, 2008,each of which is incorporated by reference herein in their entirety forall purposes. These determined geographic coordinates can be used by theelectronic device to determine the location of the electronic devicewith respect to the segments of the navigation route. If it isdetermined that the electronic device is on or within a thresholddistance from the current segment of the route (associated with thecurrently displayed direction), a negative determination can be made atblock 1206 and the process can proceed to block 1208. Alternatively, ifit is instead determined that the electronic device is not on or withina threshold distance from the current segment of the route (associatedwith the currently displayed direction) or is on or within a thresholddistance from another segment of the route, a positive determination canbe made at block 1206 and the process can proceed to block 1212 where aroute direction interface representing the route direction correspondingto the new location of the user can be displayed.

At block 1208, the electronic device (e.g., user device 602 or 604) candetermine whether a request to change the displayed direction has beenreceived. The request can be input into the electronic device in anydesired manner. For example, the request can be made by selecting abutton displayed on the displace of the first electronic device, turninga rotatable mechanism, pressing on a pressure-sensitive display,pressing a physical button on the electronic device, taping on atouch-sensitive display, performing a swipe gesture (e.g., horizontallyor vertically) across a touch-sensitive display, or the like. In someexamples, a swipe gesture detected by a touch-sensitive display thattravels from left to right on the touch-sensitive display can beinterpreted as a request to change the displayed direction to theprevious direction in the ordered set of directions, and a swipe gesturedetected by a touch-sensitive display that travels from right to left onthe touch-sensitive display can be interpreted as a request to changethe displayed direction to the next direction in the ordered set ofdirections. If it is determined that no request to change the displayeddirection has been received, the process can proceed to block 1210.However, if it is instead determined that a request to change thedisplayed direction has been received, the process can proceed to block1214 where a route direction interface representing the directionrequested to be displayed at block 1208 can be displayed.

In some examples, a downward swipe gesture (e.g., traveling from top tobottom) detected by a touch-sensitive display can be interpreted as arequest to change the displayed direction to the previous direction inthe ordered set of directions, and an upward swipe gesture (e.g.,traveling from bottom to top) detected by a touch-sensitive display canbe interpreted as a request to change the displayed direction to thenext direction in the ordered set of directions. In some examples,rather than displaying a single direction in the ordered set ofdirections on the touch-sensitive display, multiple directions of theordered set of directions are simultaneously displayed on thetouch-sensitive display (e.g., as a list). As a result, the downwardswipe gesture and the upward swipe gesture may be used to scroll throughmultiple directions in the ordered set of directions.

In some examples, an upward swipe gesture (e.g., traveling from bottomto top) detected by a touch-sensitive display can be interpreted as arequest to change the displayed direction to the previous direction inthe ordered set of directions, and an downward swipe gesture (e.g.,traveling from top to bottom) detected by a touch-sensitive display canbe interpreted as a request to change the displayed direction to thenext direction in the ordered set of directions. In some examples,rather than displaying a single direction in the ordered set ofdirections on the touch-sensitive display, multiple directions of theordered set of directions are simultaneously displayed on thetouch-sensitive display (e.g., as a list). As a result, the downwardswipe gesture and the upward swipe gesture may be used to scroll throughmultiple directions in the ordered set of directions.

At block 1210, the electronic device (e.g., user device 602 or 604) candetermine whether a request to view a map view of a displayed directionhas been received. The request can be input into the electronic devicein any desired manner. For example, the request can be made by selectinga button displayed on the displace of the first electronic device,pressing on a pressure-sensitive display, turning a rotatable mechanism,pressing a physical button on the electronic device, taping on atouch-sensitive display, performing a swipe gesture (e.g., horizontallyor vertically) across a touch-sensitive display, or the like. In someexamples, a swipe gesture detected by a touch-sensitive display thattravels from top to bottom of the touch-sensitive display can beinterpreted as a request to view a map representation of the directioncurrently being displayed. In other examples, a swipe gesture detectedby a touch-sensitive display that travels from bottom to top of thetouch-sensitive display can be interpreted as a request to view a maprepresentation of the direction currently being displayed. In otherexamples, a swipe gesture detected by a touch-sensitive display thattravels from left to right on the touch-sensitive display can beinterpreted as a request to view a map representation of the directioncurrently being displayed. In other examples, a swipe gesture detectedby a touch-sensitive display that travels from right to left on thetouch-sensitive display can be interpreted as a request to view a maprepresentation of the direction currently being displayed. If it isdetermined that no request to view the map representation has beenreceived, the process can return to block 1206. However, if it isinstead determined that a request to view the map representation hasbeen received, the process can proceed to block 1216 where a map viewinterface corresponding to the previously displayed direction (e.g., thedirection being displayed when the request to display the map view wasreceived at block 1210) can be displayed.

To illustrate the operation of process 1200, FIGS. 14-18 show exampleinterfaces that can be displayed after interface 1300 is displayed andin response to various conditions determined at blocks 1206, 1208, and1210. For example, if it is determined that a request to view the mapview has been received at block 1206 after displaying interface 1300 atblock 1204, the electronic device (e.g., user device 602 or 604) candisplay a map view interface corresponding to the previously displayeddirection (e.g., the direction being displayed when the request todisplay the map view was received at block 1210) at block 1212. FIG. 14shows an example map view interface 1400 that can be displayed by theelectronic device at block 1214 in response to receiving a request todisplay a map view while interface 1300 was being displayed. As such,interface 1400 can represent the same direction as that represented byinterface 1300. In some examples, the request can include a swipegesture from the top of the touch-sensitive display of the electronicdevice to the bottom of the touch-sensitive display. As shown, interface1400 can include a display of a map 1408 associated with the directionrepresented by the previously displayed route direction interface. Map1408 can be displayed at a position within the display and at a zoomlevel that allows current location indicator 1402 to be displayed withinmap 1408 at a position corresponding to the user's current location.Additionally, map 1408 can be displayed at a position within the displayand at a zoom level that allows the current segment of the route (e.g.,“A Street”) and the next segment of the route (e.g., “1^(st) Street”) tobe displayed along with an optional visual representation 1404 of thedirectional instruction of the current direction to navigate from thecurrent segment to the next segment of the route. Interface 1400 canfurther include combined representation 1406 including both a visualrepresentation (e.g., an arrow) of the directional instruction and atextual representation (e.g., “1^(st) Street”) of the name or identifierof the segment associated with the displayed direction. Interface 1400can further include ETA 1306 and current time 1308 similar to thoseshown in interface 1300. In some examples, route direction interface1300 can be displayed in response to receiving a request to view a routedirection view (e.g., in response to receiving a swipe gesture in adirection opposite that which caused the map view to be displayed).After displaying the map view interface at block 1216, process 1200 canreturn to block 1206

At block 1206, if it is determined that the user's location has changedor if the user's location changed from a location corresponding to theroute direction currently displayed to a location corresponding toanother route direction in the ordered set of route directions, process1200 can proceed to block 1212. At block 1212, the electronic device(e.g., user device 602 or 604) can display a route direction interfacerepresenting the route direction corresponding to the new location ofthe user. To illustrate, continuing with the example described above andshown in FIG. 13 , if it is determined that the location of theelectronic device has moved from a location on “A Street” to a locationon “1^(st) Street” (to the right of “A Street” as displayed in interface1300), the electronic device can display a new route direction interfacerepresenting the second direction of the ordered set of direction. FIG.15 illustrates an example route direction interface 1500 representingthe second direction of the ordered set of directions that can bedisplayed at block 1212. Similar to interface 1300, interface 1500 caninclude a textual representation 1302 of the displayed direction (“BearLeft On B Street”), a visual representation 1304 of a directionalinstruction associated with the direction, ETA 1306, current time 1308,and page indicator 1310, which can be updated to reflect the currentlydisplayed direction and its position relative to the other directions ofthe ordered set of directions. After the new route direction interfaceis displayed at block 1212, the process can return to block 1206.

If it is then determined that no location change has occurred at block1206, that no request to change the displayed direction is received atblock 1208, and that a request (e.g., a swipe on the touch-sensitivedisplay) to display a map view of the displayed direction is received atblock 1210 while interface 1500 is being displayed (e.g., receiving aswipe gesture from the top of the touch-sensitive display of theelectronic device to the bottom of the touch-sensitive display;receiving a swipe gesture from left to right on the touch-sensitivedisplay of the electronic device; or receiving a swipe gesture fromright to left on the touch-sensitive display of the electronic device),an interface similar to interface 1600, shown in FIG. 16 , (or interface1400 shown in FIG. 14 ) can be displayed at block 1216. As such,interface 1600 can represent the same direction as that represented byinterface 1500. In some examples, similar to interface 1400, interface1600 can include a map 1408 associated with the direction represented bythe previously displayed route direction interface (interface 1500),current location indicator 1402, visual representation 1404, combinedrepresentation 1406, ETA 1306, and current time 1308. In some examples,route direction interface 1500 can be displayed again in response toreceiving a request to view a route direction view (e.g., in response toreceiving a swipe gesture in a direction opposite that which caused themap view to be displayed). After displaying the map view interface atblock 1216, process 1200 can return to block 1206.

In some embodiments, while displaying a map view interface (e.g., 1400,1600), the device receives user input corresponding to rotation of therotatable input mechanism. In response to receiving the user inputcorresponding to the rotation of the rotatable input mechanism, thedevice pans (e.g., translates) the map view. In some examples, thedirection of the pan of the map view is based on the ordered set ofroute directions. This allows the user view different portions of themap. In some examples, the direction of the pan is along a predeterminedaxis.

If it is determined that no change in location has occurred at block1206 and that a request to change the displayed direction is received atblock 1208 while interface 1500 is being displayed, the process canproceed to block 1214. At block 1214, the electronic device (e.g., userdevice 602 or 604) can display a route direction interface representingthe direction requested to be displayed at block 1208. For example, if arequest to view the next direction in the ordered set of directions wasreceived while interface 1500 was being displayed (e.g., in response toreceiving a swipe gesture from the right of the touch-sensitive displayof the electronic device to the left of the touch-sensitive display), aninterface similar to interface 1700, shown in FIG. 17 , can bedisplayed. Similar to interface 1500, interface 1700 can include atextual representation 1302 of the displayed direction (“Turn Left On CStreet”), a visual representation 1304 of a directional instructionassociated with the direction, ETA 1306, current time 1308, and pageindicator 1310, which can be updated to reflect the currently displayeddirection and its position relative to the other directions of theordered set of directions. After the new route direction interface isdisplayed at block 1212, the process can return to block 1206.

If it is then determined that no location change has occurred at block1206, that no request to change the displayed direction is received atblock 1208, and that a request to display a map view of the displayeddirection is received at block 1210 while interface 1700 is beingdisplayed (e.g., receiving a swipe gesture from the top of thetouch-sensitive display of the electronic device to the bottom of thetouch-sensitive display), an interface similar to interface 1800, shownin FIG. 18 , can be displayed at block 1216. As such, interface 1800 canrepresent the same direction as that represented by interface 1700. Insome examples, similar to interface 1600, interface 1800 can include amap 1408 associated with the direction represented by the previouslydisplayed route direction interface (interface 1700), visualrepresentation 1404, combined representation 1406, ETA 1306, and currenttime 1308. However, unlike interface 1600, interface 1800 may notinclude current location indicator 1402 since the user is not currentlyat a location associated with the displayed direction because the usermanually selected the displayed location, rather than the displayedlocation being presented to the user in response to determining that theuser is at a location associated with the displayed location.Additionally, since the displayed direction is the last direction in theordered set of directions, interface 1800 can include a destinationindicator 1412 positioned within map 1408 at a location corresponding tothe geographic location of the destination. Destination indicator 1412can include the same or a different visual representation than currentlocation indicator 1402. In some examples, route direction interface1700 can be displayed again in response to receiving a request to view aroute direction view (e.g., in response to receiving a swipe gesture ina direction opposite that which caused the map view to be displayed).

While the blocks of process 1200 are shown in a particular order, itshould be appreciated that the blocks can be performed in any order andsome blocks may not be performed at all. For example, blocks 1206, 1208,and 1210 can be evaluated in any order and with any desired frequency orat any desired interval of time to determine whether the displayedinterface should be changed based on the user's location, a request tochange the displayed direction, and a request to display a map view,respectively.

Using process 1200, individual route directions can be presented to auser in manner that allows the user to easily identify the nextdirection in the route with a quick glance at the user device.Additionally, process 1200 advantageously allows a user to scrollthrough previous or subsequent directions and to view maprepresentations of the directions to obtain a better understanding ofthe route being displayed.

FIG. 19 illustrates an exemplary process 1900 for selectively displayingrepresentations of a mapping application according to various examples.In some examples, process 1900 can be performed using electronic devicessimilar or identical to device 100, 300, 500, 602, or 604.

At block 1902 of process 1900, an electronic device (e.g., device 602 or604) can detect a triggering event for activating a display of theelectronic device. The triggering event can include any predefined oruser-selected event. In some examples, detecting the triggering eventcan include detecting that the electronic device is moved into aposition that can be viewed by a user. For example, if the electronicdevice is a wearable electronic device, such as a watch, detecting thetriggering event can include detecting that the watch is raised andoriented in a direction that would be viewable by the user. In otherexamples, the triggering event can include the depression of a physicalbutton, a touch on a touch-sensitive display, a press on apressure-sensitive display, or the like. In response to detecting thetriggering event, process 1900 can proceed to block 1904.

At block 1904, the electronic device (e.g., device 602 or 604) canobtain contextual data representing a context of the electronic device.In general, the contextual data can include any type of informationassociated with the user input that can be used to infer the user'sintent. In some examples, the contextual data can include sensorinformation from user device 602 or 604, such as lighting, ambientnoise, ambient temperature, images or videos of the surroundingenvironment, distance to another object, and the like. The contextualinformation can additionally or alternatively include informationassociated with the physical state of user device 602 or 604, such asthe device orientation, device location, device temperature, powerlevel, speed, acceleration, motion patterns, cellular signal strength,etc., or the software state of user device 602 or 604, such as runningprocesses, installed programs, past and present network activities,background services, error logs, resources usage, contents displayed onthe device, contents of a portion of a map displayed on the device,length of time that a current view has been displayed on the device,length of time since receiving a user input, length of time anapplication has been opened or running, etc. The contextual data canadditionally or alternatively include information associated with theuser, such as the user's contact list, calendar, task or to-do list,historical activity data, preferences, or the like.

At block 1906, the electronic device (e.g., device 602 or 604) candetermine, based on the contextual data obtained at block 1904, whetherit is likely that the user will be traveling to a destination within athreshold length of time. This determination can be made, for example,based on the contextual data obtained at block 1904, which can includeappointments (having locations and times) in the user's calendar, items(having locations and times) in the user's task or to-do list, a patternof the user traveling to the same destination at the same time based onthe historical activity of the user, or the like. The threshold lengthof time can be a predetermined value or can vary depending on thecurrent location of the user and the location of the destination of thepredicted travel. For example, the threshold length of time can begreater than or equal to an estimated travel time required for the userto travel from his/her current location to the destination of thepredicted travel. This can depend on, for example, the distance to thedestination, type of roads being traveled, traffic conditions, theuser's mode of the transportation, length of time previously required totravel the same route, or the like. If it is determined that it islikely the user will be traveling, process 1900 can proceed to block1908. Alternatively, if it is instead determined that it is not likelythat the user will be traveling, process 1900 can proceed to block 1910.

At block 1908, the electronic device (e.g., device 602 or 604) candisplay an interface representing a mapping application based on thetraveling predicted to be performed by the user determined at block1906. The interface can generally include an affordance for opening orlaunching the mapping application and a set of data associated with thepredicted traveling obtained from the mapping application that can beupdated based on data from the application. The set of data associatedwith the predicted travel can include an estimated time of arrival atthe destination, an estimated length of time to travel to thedestination, one or more directions for traveling to destination, a mapcomprising at least a portion of a route to the destination, trafficinformation associated with the route to the destination, or the like.For example, an interface similar to interface 2000, shown in FIG. 20 ,can be displayed by the electronic device at block 1908. Interface 2000can display a set of data obtained from the mapping application usingthe predicted travel determined at block 1906 as an input. For example,interface 2000 can include elements similar to interface 1300, describedabove, such as a textual representation 1302, visual representation1304, and page indicator 1310 representing a direction of a set ofdirections for traveling to the destination of the predicted traveldetermined at block 1906 as determined by the mapping application. Asthe user moves, the displayed direction can be updated based on thecurrent direction of the set of directions as determined by the mappingapplication. Additionally, interface 2000 can further include anestimated time of arrival represented by ETA 1306 and a current timerepresented by current time 1308.

In some examples, interface 2000 can include an affordance, such as atext label or icon, for opening or launching the represented mappingapplication. The affordance can include any portion or the entirety ofthe interface. For example, the affordance can include a virtual buttonor can include all of interface 2000. The electronic device can open therepresented mapping application in response to selection of theaffordance. For example, the electronic device can open the mappingapplication in response to a tap on a touch-sensitive display, a presson a pressure-sensitive display, a swipe gesture performed across atouch-sensitive display, a depression of a physical button, a turn of arotatable mechanism, a selection of a displayed option, or the like,while interface 2000 is displayed. In some examples, the mappingapplication can be opened using the predicted travel determined at block1906 as an input. For example, the mapping application can be opened andthe predicted travel can be entered as a desired destination for anavigation route.

In some examples, interface 2000 can be generated using a process orapplication separate from the mapping application that it represents. Inthese examples, the mapping application may not be displayed and mayinstead be executed in the background.

FIG. 21 illustrates another example interface 2100 that can be displayedat block 1908. Interface 2100 can display a set of data associated withthe predicted traveling and obtained from the mapping application usingthe predicted travel determined at block 1906 as an input. For example,interface 2100 can include elements similar to interface 1400, describedabove, such as map 1408 and visual representation 1404 representing adirection of a set of directions for traveling to the destination of theexpected travel determined at block 1906 as determined by the mappingapplication. As the user moves, the displayed direction can be updatedbased on the current direction of the set of directions as determined bythe mapping application. Additionally, interface 2100 can furtherinclude current location indicator 1402, an estimated time of arrivalrepresented by ETA 1306, and a current time represented by current time1308.

In some examples, interface 2000 can include an affordance, such as atext label or icon, for opening or launching the represented mappingapplication. The affordance can include any portion or the entirety ofthe interface. For example, the affordance can include a virtual buttonor can include all of interface 2000. The electronic device can open therepresented mapping application in response to selection of theaffordance. For example, the electronic device can open the mappingapplication in response to a tap on a touch-sensitive display, a presson a pressure-sensitive display, a swipe gesture performed across atouch-sensitive display, a depression of a physical button, a turn of arotatable mechanism, a selection of a displayed option, or the like,while interface 2000 is displayed. In some examples, the mappingapplication can be opened using the expected travel determined at block1906 as an input. For example, the mapping application can be opened andthe expected travel can be entered as a desired destination for anavigation route.

In some examples, interface 2100 can be generated using a process orapplication separate from the mapping application that it represents. Inthese examples, the mapping application may not be displayed and mayinstead be executed in the background.

At block 1910, the electronic device (e.g., device 602 or 604) candisplay an interface representing a mapping application based on thecurrent location of the user since no predicted travel was determined atblock 1906. The interface can generally include an affordance foropening or launching the mapping application and information associatedwith the user's current location. For example, an interface similar tointerface 2200, shown in FIG. 22 , can be displayed by the electronicdevice at block 1910. Interface 2200 can include elements similar tointerface 1400, described above, such as current location indicator1402, map 1408, and current time 1308. Since no travel is expected,there may not be navigation route to a destination. As a result,interface 2200 may not include visual representation 1404 or ETA 1306.In some examples, interface 2200 can include an affordance for openingor launching the represented mapping application. The affordance caninclude any portion or the entirety of the interface. For example, theaffordance can include a virtual button or can include all of interface2200. The electronic device can open the represented mapping applicationin response to selection of the affordance. For example, the electronicdevice can open the mapping application in response to a tap on atouch-sensitive display, a press on a pressure-sensitive display, aswipe gesture performed across a touch-sensitive display, a depressionof a physical button, a turn of a rotatable mechanism, a selection of adisplayed option, or the like, while interface 2200 is displayed. Insome examples, the mapping application can be opened and can display theuser's current location since no navigation route to a destination hasbeen determined.

Using process 1900, an electronic device can advantageously present theuser with an interface containing an affordance for easily opening amapping application. Additionally, the interface can advantageouslymodify the type of information presented in the interface to includeinformation that is likely relevant to the user as determined by theelectronic device based on contextual information. Moreover, theelectronic device can launch the mapping application using theinformation displayed within the interface to reduce the amount of inputrequired from the user to cause the mapping application to perform adesired function.

FIG. 23 shows a functional block diagram of an electronic device 2300configured in accordance with the principles of the various describedexamples. The functional blocks of the device can be implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 23 can be combined or separated into sub-blocks to implement theprinciples of the various described examples. Therefore, the descriptionherein optionally supports any possible combination or separation orfurther definition of the functional blocks described herein.

As shown in FIG. 23 , electronic device 2300 can include a display unit2304 configured to display graphical objects, a touch-sensitive surfaceunit 2302 configured to receive user gestures, and a processing unit2308. In some examples, processing unit 2308 can include an audioreceiving unit 2310, a contextual data receiving unit 2312, a generatingunit 2314, a text transmitting unit 2316, a map data receiving unit2318, and a map data transmitting unit 2320.

Processing unit 2308 can be configured to receive (e.g., using audioreceiving unit 2310) data corresponding to an audio input comprisinguser speech. Contextual data receiving unit 2312 can be configured toreceive contextual data representing a context of the user speech.Generating unit 2314 can generate a textual representation of the userspeech based on the data corresponding to the audio input. Texttransmitting unit 2316 can transmit, to a map server, the textualrepresentation of the user speech and the contextual data. Map datareceiving unit 2318 can receive, from the map server, map data and mapdata transmitting unit 2320 can transmit the map data to the electronicdevice.

In some examples, the contextual data can include a location of theelectronic device. In other examples, the contextual data can include asoftware state of the electronic device. In other examples, thecontextual data can include a content being displayed by the electronicdevice. In other examples, the contextual data can include a state of amapping application running on the electronic device. In some examples,the current state of the mapping application can include a current viewof the mapping application being displayed on the electronic device. Insome examples, the current state of the mapping application can includea length of time that the current view of the mapping application hasbeen displayed. In some examples, the contextual data can include lengthof time since the electronic device received a user input.

In some examples, the map data can include: one or more map tiles, a setof geographic coordinates, routing information from a start location toan end location, or traffic data. In some examples, the textualrepresentation of the user speech is not transmitted to the electronicdevice.

FIG. 24 shows a functional block diagram of an electronic device 2400configured in accordance with the principles of the various describedexamples. The functional blocks of the device can be implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 24 can be combined or separated into sub-blocks to implement theprinciples of the various described examples. Therefore, the descriptionherein optionally supports any possible combination or separation orfurther definition of the functional blocks described herein.

As shown in FIG. 24 , electronic device 2400 can include a display unit2404 configured to display graphical objects, a touch-sensitive surfaceunit 2402 configured to receive user gestures, and a processing unit2408. In some examples, processing unit 2408 can include a mapdisplaying unit 2410, a determining unit 2412, a first location markerdisplaying unit 2414, a first geographic coordinate transmitting unit2416, a storing unit 2418, a second location marker displaying unit2420, a second coordinate transmitting unit 2422, a receiving unit 2424,and a third location marker displaying unit 2426.

Processing unit 2408 can be configured to cause (e.g., using mapdisplaying unit 2410), on a display of a first electronic device, adisplay of a map. Determining unit 2412 can determine whether a firstrequest to mark a first location on the map has been received. Firstlocation marker displaying unit 2414 can cause, on the display of thefirst electronic device, a display of a first location marker on the mapat a position within the display corresponding to the first location inaccordance with a determination that the first request to mark the firstlocation on the map has been received. First geographic coordinatetransmitting unit 2416 can transmit, to a second electronic device, afirst set of geographic coordinates corresponding to the first locationin accordance with a determination that the first request to mark thefirst location on the map has been received.

In some examples, storing unit 2418 can be configured to store, at thefirst electronic device, the first set of geographic coordinates.

In some examples, first location marker displaying unit 2414 can befurther configured to cause, on the display of the first electronicdevice, a display of information associated with the first location. Insome examples, the information associated with the first location caninclude an address, a street name, a name of a city, a name of acountry, a zip code, or an estimated travel time to the first location.

In some examples, determining unit 2412 can be configured to determinewhether the first request to mark the first location on the map has beenreceived by determining whether a touch has been detected at theposition within the display corresponding to the first location for morethan a threshold length of time.

In some examples, determining unit 2412 can be further configured todetermine whether a second request to mark a second location on the maphas been received. Second location marker displaying unit 2420 can beconfigured to cause, on the display of the first electronic device, adisplay of a second location marker overlaid on the map at a positionwithin the display corresponding to the second location in accordancewith a determination that the second request to mark the second locationon the map has been received. Second coordinate transmitting unit 2422can be configured to transmit, to the second electronic device, a secondset of geographic coordinates corresponding to the second location inaccordance with a determination that the second request to mark thesecond location on the map has been received.

In some examples, second location marker displaying unit 2420 canconfigured to cause, on the display of the first electronic device, thedisplay of the second location marker overlaid on the map by removingthe first location marker from the display of the first electronicdevice. In some examples, storing unit 2418 can be configured to replacethe stored first set of geographic coordinates with the second set ofgeographic coordinates.

In some examples, receiving unit 2424 can be configured to receive, atthe first electronic device, a third set of geographic coordinates fromthe second electronic device. In some examples, storing unit 2418 can befurther configured to replace the stored first set of geographiccoordinates with the third set of geographic coordinates. In someexamples, third location marker displaying unit 2426 can be configuredto cause, on the display of the first electronic device, a display of athird location marker overlaid on the map at a position within thedisplay corresponding to the third set of geographic coordinates.

In some examples, third location marker displaying unit 2426 can befurther configured to cause, on the display of the first electronicdevice, the display of the third location marker overlaid on the mapfurther by removing the first location marker from the display of thefirst electronic device.

FIG. 25 shows a functional block diagram of an electronic device 2500configured in accordance with the principles of the various describedexamples. The functional blocks of the device can be implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 25 can be combined or separated into sub-blocks to implement theprinciples of the various described examples. Therefore, the descriptionherein optionally supports any possible combination or separation orfurther definition of the functional blocks described herein.

As shown in FIG. 25 , electronic device 2500 can include a display unit2504 configured to display graphical objects, a touch-sensitive surfaceunit 2502 configured to receive user gestures, and a processing unit2508. In some examples, processing unit 2508 can include a receivingunit 2510, a displaying unit 2512, and a determining unit 2514.

Processing unit 2508 can be configured to receive (e.g., using receivingunit 2510) an ordered set of route directions for navigating a routefrom a start location to an end location, wherein the route comprises aplurality of segments. Displaying unit 2512 can cause a display of firstroute direction interface associated with a first route direction of theset of route directions, wherein the first route direction is associatedwith a first segment of the plurality of segments and comprises a firstdirectional instruction and a first segment identifier associated withthe first segment, and wherein the first route direction interfacecomprises: a first textual description of the first directionalinstruction and the first segment identifier and a first visualrepresentation of the first directional instruction.

In some examples, the first route direction interface excludes a map. Insome examples, the first route direction interface excludes a view ofany of the plurality of segments. In some examples, the first visualrepresentation consists of an image of an arrow. In some examples, thefirst directional instruction includes an instruction to turn or aninstruction to travel straight. In some examples, the first routedirection interface further includes an estimated time of arrival at theend location.

In some examples, determining unit 2515 can be configured to determinewhether a location of the electronic device corresponds to a secondsegment of the plurality of segments. In some examples, displaying unit2512 can be configured to replace, in accordance with a determinationthat the location of the electronic device corresponds to the secondsegment of the plurality of segments, the first route directioninterface with a second route direction interface associated with asecond route direction of the set of route directions, wherein thesecond route direction is associated with the second segment of theplurality of segments and comprises a second directional instruction anda second segment identifier associated with the second segment, andwherein the second route direction interface comprises a second textualdescription of the second directional instruction and the second segmentidentifier and a second visual representation of the second directionalinstruction.

In some examples, determining unit 2512 can be configured to determinewhether a request to view a third direction of the set of routedirections has been received. In some examples, displaying unit 2512 canbe configured to replace, in accordance with a determination that therequest to view the third direction of the set of route directions hasbeen received, the first route direction interface with a third routedirection interface associated with a third route direction of the setof route directions, wherein the third route direction is associatedwith the third segment of the plurality of segments and comprises athird directional instruction and a third segment identifier associatedwith the third segment, and wherein the third route direction interfacecomprises: a third textual description of the third directionalinstruction and the third segment identifier and a third visualrepresentation of the third directional instruction.

In some examples, determining unit 2512 can be configured to determinewhether the request to view the third direction of the set of routedirections has been received by determining whether a swipe gesture hasbeen detected across the display of the electronic device. In someexamples, the swipe gesture includes a horizontal swipe gesture.

In some examples, determining unit 2514 can be configured to determinewhether a request to view a map view of the first direction has beenreceived. In some examples, displaying unit 2512 can be configured toreplace, in accordance with a determination that the request to view themap view of the first direction has been received, the first routedirection interface with a first map view interface associated with thefirst route direction, wherein the first map view interface comprises amap comprising the first segment and a combined textual and visualrepresentation of the first direction.

In some examples, determining unit 2514 can be configured to determinewhether the request to view the map view of the first direction has beenreceived by determining whether a swipe gesture has been detected acrossthe display of the electronic device. In some examples, the swipegesture includes a vertical swipe gesture.

FIG. 26 shows a functional block diagram of an electronic device 2600configured in accordance with the principles of the various describedexamples. The functional blocks of the device can be implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 26 can be combined or separated into sub-blocks to implement theprinciples of the various described examples. Therefore, the descriptionherein optionally supports any possible combination or separation orfurther definition of the functional blocks described herein.

As shown in FIG. 26 , electronic device 2600 can include a display unit2604 configured to display graphical objects, a touch-sensitive surfaceunit 2602 configured to receive user gestures, and a processing unit2608. In some examples, processing unit 2608 can include a detectingunit 2610, obtaining unit 2612, determining unit 2614, first displayingunit 2616, and a second displaying unit 2618.

Processing unit 2608 can be configured to detect (e.g., using detectingunit 2610) a display triggering event. Obtaining unit 2612 can beconfigured to obtain contextual data representing a context of theelectronic device in accordance with a detection of the displaytriggering event. Determining unit 2614 can be configured to determine,based on the contextual data, whether a user is likely to be travelingto a destination within a threshold length of time. First displayingunit 2616 can be configured to cause a display of a first interfacerepresenting a mapping application in accordance with a determinationthat the user is likely to be traveling to the destination within thethreshold length of time, wherein the first interface representing themapping application comprises: a first affordance for launching themapping application and a set of information associated with travelingto the destination. Second displaying unit 2616 can be configured tocause a display of a second interface representing the mappingapplication in accordance with a determination that the user is notlikely to be traveling to the destination within the threshold length oftime, wherein the second interface representing the mapping applicationcomprises: a second affordance for launching the mapping application anda visual representation of a location of the electronic device.

In some examples, the threshold length of time is greater than or equalto an estimated travel time to the destination.

In some examples, the contextual data comprises the user's calendar dataand determining unit 2614 can be configured to determine whether theuser is likely to be traveling to a destination by determining whetherthe user has a scheduled appointment within the threshold length of timebased on the calendar data, the scheduled appointment associated withthe destination.

In some examples, the contextual data includes the user's task list dataand determining unit 2614 can be configured to determine whether theuser is likely to be traveling to a destination by determining whetherthe user has a scheduled task to perform within the threshold length oftime based on the task list data, the scheduled task associated with thedestination.

In some examples, the contextual data includes the user's historicalactivity data and determining unit 2614 can be configured to determinewhether the user is likely to be traveling to a destination bydetermining whether the user has a pattern of traveling to thedestination at a time during a day, wherein the time during the day iswithin the threshold length of time from a current time.

In some examples, the set of information associated with traveling tothe destination includes: an estimated time of arrival at thedestination, an estimated length of time to travel to the destination,one or more directions for traveling to destination, a map comprising atleast a portion of a route to the destination, or traffic informationassociated with the route to the destination.

In some examples, the mapping application is executing on the electronicdevice and is not displayed on the display.

In some examples, detecting unit 2610 can be further configured todetect a selection of the first affordance and first displaying unit2616 can be configured to replace, in response to detecting theselection of the first affordance, the display of the first interfacewith a display of the mapping application.

In some examples, detecting unit 2610 can be further configured todetect a selection of the second affordance and second displaying unit2618 can be configured to replace, in response to detecting theselection of the second affordance, the display of the second interfacewith a display of the mapping application.

In some examples, the display triggering event includes the electronicdevice being oriented in a predetermined orientation. In other examplesthe display triggering event includes a touch detected at the display ofthe electronic device.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improve thedelivery to users of invitational content or any other content that maybe of interest to them. The present disclosure contemplates that in someinstances, this gathered data may include personal information data thatuniquely identifies or can be used to contact or locate a specificperson. Such personal information data can include demographic data,location-based data, telephone numbers, email addresses, home addresses,or any other identifying information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todeliver targeted content that is of greater interest to the user.Accordingly, use of such personal information data enables calculatedcontrol of the delivered content. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure.

The present disclosure further contemplates that the entitiesresponsible for the collection, analysis, disclosure, transfer, storage,or other use of such personal information data will comply withwell-established privacy policies and/or privacy practices. Inparticular, such entities should implement and consistently use privacypolicies and practices that are generally recognized as meeting orexceeding industry or governmental requirements for maintaining personalinformation data private and secure. For example, personal informationfrom users should be collected for legitimate and reasonable uses of theentity and not shared or sold outside of those legitimate uses. Further,such collection should occur only after receiving the informed consentof the users. Additionally, such entities would take any needed stepsfor safeguarding and securing access to such personal information dataand ensuring that others with access to the personal information dataadhere to their privacy policies and procedures. Further, such entitiescan subject themselves to evaluation by third parties to certify theiradherence to widely accepted privacy policies and practices.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof advertisement delivery services, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services. In another example, users can select not toprovide location information for targeted content delivery services. Inyet another example, users can select to not provide precise locationinformation, but permit the transfer of location zone information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publically available information.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: detecting a display triggering event,wherein the display triggering event comprises the electronic devicebeing oriented in a predetermined orientation; in accordance with adetection of the display triggering event, obtaining contextual datarepresenting a context of the electronic device; determining, based onthe contextual data, whether a user is likely to be traveling to adestination within a threshold length of time; in accordance with adetermination that the user is likely to be traveling to the destinationwithin the threshold length of time, causing, on the display, a displayof a first interface representing a mapping application, wherein thefirst interface representing the mapping application comprises: a set ofinformation associated with traveling to the destination; and inaccordance with a determination that the user is not likely to betraveling to the destination within the threshold length of time,causing, on the display, a display of a second interface representingthe mapping application, wherein the second interface representing themapping application comprises: a visual representation of a location ofthe electronic device.
 2. The electronic device of claim 1, wherein thethreshold length of time is greater than or equal to an estimated traveltime to the destination.
 3. The electronic device of claim 1, whereinthe contextual data comprises calendar data of the user, and whereindetermining whether the user is likely to be traveling to a destinationcomprises determining whether the user has a scheduled appointmentwithin the threshold length of time based on the calendar data, thescheduled appointment associated with the destination.
 4. The electronicdevice of claim 1, wherein the contextual data comprises task list dataof the user, and wherein determining whether the user is likely to betraveling to a destination comprises determining whether the user has ascheduled task to perform within the threshold length of time based onthe task list data, the scheduled task associated with the destination.5. The electronic device of claim 1, wherein the contextual datacomprises historical activity data of the user, and wherein determiningwhether the user is likely to be traveling to a destination comprisesdetermining whether the user has a pattern of traveling to thedestination at a time during a day, wherein the time during the day iswithin the threshold length of time from a current time.
 6. Theelectronic device of claim 1, wherein the set of information associatedwith traveling to the destination comprises: an estimated time ofarrival at the destination; an estimated length of time to travel to thedestination; one or more directions for traveling to the destination; amap comprising at least a portion of a route to the destination; ortraffic information associated with the route to the destination.
 7. Theelectronic device of claim 1, wherein the mapping application isexecuting on the electronic device and wherein causing display of thefirst interface representing the mapping application does not includedisplaying the mapping application.
 8. The electronic device of claim 1,the one or more programs further including instructions for: detecting aselection of a first affordance for launching the mapping application;and in response to detecting the selection of the first affordance,replacing the display of the first interface with a display of themapping application.
 9. The electronic device of claim 1, the one ormore programs further including instructions for: detecting a selectionof a second affordance for launching the mapping application; and inresponse to detecting the selection of the second affordance, replacingthe display of the second interface with a display of the mappingapplication.
 10. The electronic device of claim 1, wherein the displaytriggering event includes activating the display of the electronicdevice.
 11. A non-transitory computer-readable storage medium storingone or more programs configured to be executed by one or more processorsof an electronic device with a display, the one or more programsincluding instructions for: detecting a display triggering event,wherein the display triggering event comprises the electronic devicebeing oriented in a predetermined orientation; in accordance with adetection of the display triggering event, obtaining contextual datarepresenting a context of the electronic device; determining, based onthe contextual data, whether a user is likely to be traveling to adestination within a threshold length of time; in accordance with adetermination that the user is likely to be traveling to the destinationwithin the threshold length of time, causing, on the display, a displayof a first interface representing a mapping application, wherein thefirst interface representing the mapping application comprises: a set ofinformation associated with traveling to the destination; and inaccordance with a determination that the user is not likely to betraveling to the destination within the threshold length of time,causing, on the display, a display of a second interface representingthe mapping application, wherein the second interface representing themapping application comprises: a visual representation of a location ofthe electronic device.
 12. The non-transitory computer-readable storagemedium of claim 11, wherein the threshold length of time is greater thanor equal to an estimated travel time to the destination.
 13. Thenon-transitory computer-readable storage medium of claim 11, wherein thecontextual data comprises calendar data of the user, and whereindetermining whether the user is likely to be traveling to a destinationcomprises determining whether the user has a scheduled appointmentwithin the threshold length of time based on the calendar data, thescheduled appointment associated with the destination.
 14. Thenon-transitory computer-readable storage medium of claim 11, wherein thecontextual data comprises task list data of the user, and whereindetermining whether the user is likely to be traveling to a destinationcomprises determining whether the user has a scheduled task to performwithin the threshold length of time based on the task list data, thescheduled task associated with the destination.
 15. The non-transitorycomputer-readable storage medium of claim 11, wherein the contextualdata comprises historical activity data of the user, and whereindetermining whether the user is likely to be traveling to a destinationcomprises determining whether the user has a pattern of traveling to thedestination at a time during a day, wherein the time during the day iswithin the threshold length of time from a current time.
 16. Thenon-transitory computer-readable storage medium of claim 11, wherein theset of information associated with traveling to the destinationcomprises: an estimated time of arrival at the destination; an estimatedlength of time to travel to the destination; one or more directions fortraveling to the destination; a map comprising at least a portion of aroute to the destination; or traffic information associated with theroute to the destination.
 17. The non-transitory computer-readablestorage medium of claim 11, wherein the mapping application is executingon the electronic device and wherein causing display of the firstinterface representing the mapping application does not includedisplaying the mapping application.
 18. The non-transitorycomputer-readable storage medium of claim 11, the one or more programsfurther including instructions for: detecting a selection of a firstaffordance for launching the mapping application; and in response todetecting the selection of the first affordance, replacing the displayof the first interface with a display of the mapping application. 19.The non-transitory computer-readable storage medium of claim 11, the oneor more programs further including instructions for: detecting aselection of a second affordance for launching the mapping application;and in response to detecting the selection of the second affordance,replacing the display of the second interface with a display of themapping application.
 20. The non-transitory computer-readable storagemedium of claim 11, wherein the threshold length of time is greater thanor equal to an estimated travel time to the destination.
 21. Thenon-transitory computer-readable storage medium of claim 11, wherein thedisplay triggering event includes activating the display of theelectronic device.
 22. A method, comprising: at an electronic devicecomprising a display: detecting a display triggering event, wherein thedisplay triggering event comprises the electronic device being orientedin a predetermined orientation; in accordance with a detection of thedisplay triggering event, obtaining contextual data representing acontext of the electronic device; determining, based on the contextualdata, whether a user is likely to be traveling to a destination within athreshold length of time; in accordance with a determination that theuser is likely to be traveling to the destination within the thresholdlength of time, causing, on the display, a display of a first interfacerepresenting a mapping application, wherein the first interfacerepresenting the mapping application comprises: a set of informationassociated with traveling to the destination; and in accordance with adetermination that the user is not likely to be traveling to thedestination within the threshold length of time, causing, on thedisplay, a display of a second interface representing the mappingapplication, wherein the second interface representing the mappingapplication comprises: a visual representation of a location of theelectronic device.
 23. The method of claim 22, wherein the contextualdata comprises calendar data of the user, and wherein determiningwhether the user is likely to be traveling to a destination comprisesdetermining whether the user has a scheduled appointment within thethreshold length of time based on the calendar data, the scheduledappointment associated with the destination.
 24. The method of claim 22,wherein the contextual data comprises task list data of the user, andwherein determining whether the user is likely to be traveling to adestination comprises determining whether the user has a scheduled taskto perform within the threshold length of time based on the task listdata, the scheduled task associated with the destination.
 25. The methodof claim 22, wherein the contextual data comprises historical activitydata of the user, and wherein determining whether the user is likely tobe traveling to a destination comprises determining whether the user hasa pattern of traveling to the destination at a time during a day,wherein the time during the day is within the threshold length of timefrom a current time.
 26. The method of claim 22, wherein the set ofinformation associated with traveling to the destination comprises: anestimated time of arrival at the destination; an estimated length oftime to travel to the destination; one or more directions for travelingto the destination; a map comprising at least a portion of a route tothe destination; or traffic information associated with the route to thedestination.
 27. The method of claim 22, wherein the mapping applicationis executing on the electronic device and wherein causing display of thefirst interface representing the mapping application does not includedisplaying the mapping application.
 28. The method of claim 22, furthercomprising, at the electronic device: detecting a selection of a firstaffordance for launching the mapping application; and in response todetecting the selection of the first affordance, replacing the displayof the first interface with a display of the mapping application. 29.The method of claim 22, further comprising, at the electronic device:detecting a selection of a second affordance for launching the mappingapplication; and in response to detecting the selection of the secondaffordance, replacing the display of the second interface with a displayof the mapping application.
 30. The method of claim 22, wherein thedisplay triggering event includes activating the display of theelectronic device.